Control method and information processing apparatus

ABSTRACT

There is provided a control method for an information processing apparatus that stores an editing application with which editing of intermediate data including drawing data generated by a drawing application can be performed, the control method including: obtaining information associated with a print setting; deciding an interface used for obtaining the intermediate data from among a plurality of interfaces on a basis of the obtained information associated with the print setting; and obtaining the intermediate data by using the decided interface, in which the intermediate data output from the editing application is obtained by a printer driver and converted into a print command.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 16/299,753, filed on Mar. 12, 2019, which claims priority fromJapanese Patent Application No. 2018-048200 filed Mar. 15, 2018, whichare hereby incorporated by reference herein in their entireties.

BACKGROUND OF THE INVENTION Field of the Invention

The present invention relates to a control method and an informationprocessing apparatus. In particular, the invention relates to a controlmethod of an editing application and an information processingapparatus.

Description of the Related Art

A configuration has been generally proposed in which a printer driverinstalled into a host computer as software for controlling a printingapparatus is used, and printing is performed with respect to theprinting apparatus connected to the host computer. An operating system(OS) corresponding to basic software is installed into the hostcomputer. The printer driver is configured in accordance with aspecification specified by the OS and operates when the printer driveris called from the OS. When a vender that provides the printingapparatus provides the printer driver adapted to the specification ofthe OS, it is possible to provide a unit configured to instruct theprinter to perform printing by using the OS. In a case where a versionbefore Microsoft (registered trademark) Windows (registered trademark) 8is used as the OS, the printer driver is configured by an architecturecalled V3 printer driver. The V3 printer driver displays a graphicaluser interface (hereinafter, which will be also referred to as “GUI” or“user interface”) at a timing when a print request from a user isgenerated. According to this GUI, it is possible to provide a functionfor urging the user to perform any operation. For example, when theprint request is generated, since a specified event of a configurationmodule corresponding to a component of the V3 printer driver is called,the configuration module can display the user interface in the eventprocessing.

In recent years, a new architecture called V4 printer driver has enteredthe market in Windows (registered trademark). Since the V4 printerdriver puts a high priority on security performance, customizationperformance of the printer driver itself is decreased. For example, theabove-described configuration module is provided by the OS, and thevender can provide only a setting file for customizing the operation ora script file. To compensate the above-described decrease incustomization performance, the vender that provides the printingapparatus can provide a dedicated-use application for extending thefunction of the printer driver. An application called Windows StoreDevice App (WSDA) has been proposed as this application. When the venderthat provides the printing apparatus can customize a print settingscreen used when drawing data is to be printed by providing the WSDA(Japanese Patent Laid-Open No. 2017-33052).

SUMMARY OF THE INVENTION

A control method according to an aspect of the present invention relatesto a control method for an information processing apparatus that storesan editing application with which editing of intermediate data includingdrawing data generated by a drawing application can be performed, thecontrol method comprising obtaining information associated with a printsetting, deciding an interface used for obtaining the intermediate datafrom among a plurality of interfaces on a basis of the obtainedinformation associated with the print setting, and obtaining theintermediate data by using the decided interface, wherein theintermediate data output from the editing application is obtained by aprinter driver and converted into a print command.

Further features of the present invention will become apparent from thefollowing description of exemplary embodiments with reference to theattached drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating a hardware configuration of aprinting system.

FIG. 2 is a block configuration diagram of a driver printing system.

FIGS. 3A to 3C are schematic diagrams for describing a screen in a casewhere a print instruction is performed.

FIG. 4 is a flow chart of setup processing of an editing application.

FIG. 5 illustrates an example of Print Capabilities.

FIG. 6 illustrates an example of Print Ticket.

FIG. 7 is a flow chart of UI processing of the editing application.

FIG. 8 is a schematic diagram of a user interface of the editingapplication.

FIG. 9 is a flow chart of editing and end processing of the editingapplication.

FIG. 10 illustrates an example of information stored in Local Storage.

FIG. 11 is a flow chart of editing and end processing of the editingapplication according to a second exemplary embodiment.

FIG. 12 is a flow chart of editing and end processing of the editingapplication according to a third exemplary embodiment.

FIG. 13 is a conceptual diagram of a logic structure of XPS.

DESCRIPTION OF THE EMBODIMENTS

While security performance or usability of a V4 printer driver isimproved, customization performance of the printer driver itself isdecreased because, for example, the V4 printer driver does not include afunction for providing a GUI. Therefore, as described in Japanese PatentLaid-Open No. 2017-33052, even in a case where a driver that does notinclude the function for providing the GUI like the V4 printer driver isused, it is possible to provide the GUI such as the print setting screenby using the WSDA. However, the related-art WSDA still has arestriction. In addition, an application called Printer Extensions (PEX)has also been proposed as the application for extending the function ofthe printer driver, but this PEX also has a restriction similar to thatof the WSDA. The present invention has been made in view of theabove-described issues and aims at providing a technology for providinga more appropriate function in accordance with a setting.

According to the following respective exemplary embodiments, a moreappropriate function is provided by using an application called PrintWorkflow Application (WFA). This WFA is an editing application withwhich editing of intermediate data including drawing data generated by adrawing application can be performed. Since the editing application isactivated in accordance with a print request, the editing application isalso referred to as a printing-time activation application. A detail ofthe editing application will be described below.

Hereinafter, exemplary embodiments of the present invention will bedescribed in detail with reference to the accompanying drawings. Itshould be noted that the following exemplary embodiments are notintended to limit the present invention described in the scope of theinvention, and all of combinations of features described according tothe present exemplary embodiment are not necessarily essential to adevice for solving for the present invention.

First Exemplary Embodiment

FIG. 1 is a block diagram illustrating a hardware configuration of aprinting system. In FIG. 1, a host computer 101 is an example of aninformation processing apparatus. The host computer 101 includes aninput interface 110, a central processing unit (CPU) 111, a read onlymemory (ROM) 112, a random access memory (RAM) 113, an external storagedevice 114, an output interface 115, and an input and output interface116. Input devices such as a keyboard 118 and a pointing device 117 areconnected to the input interface 110. A display device such as a displayunit 119 is connected to the output interface 115.

The ROM 112 stores an initialization program, and the external storagedevice 114 stores a group of application programs, an operating system(OS), a printer driver, and other various data. The RAM 113 is used as awork memory or the like when the various programs stored in the externalstorage device 114 are executed.

It should be noted that, according to the present exemplary embodiment,when the CPU 111 performs processing in accordance with a procedure ofthe program stored in the ROM 112, a function which will be describedbelow in the host computer 101 and processing related to a flow chartwhich will also be described below are realized. The printing apparatus102 functioning as a device is connected to the host computer 101 viathe input and output interface 116. Herein, the host computer 101 andthe printing apparatus 102 are separately constituted, but theseapparatuses may also be constituted as a single information processingapparatus.

Block Configuration of Driver Printing System

FIG. 2 is a block configuration diagram of a driver printing system.Herein, descriptions will be provided while it is assumed that the hostcomputer 101 in which an OS of Microsoft (registered trademark) Windows(registered trademark) 8 or a subsequent version is installed as the OSis used, and a printing system operating under an architecture called V4printer driver is adopted. It should be noted that descriptions will beprovided while a model specific printer driver functioning as a printerdriver dedicated to the model of the printing apparatus 102 which isprovided by the printer vender is used as the printer driver accordingto the present exemplary embodiment, for example. However, the printerdriver according to the present exemplary embodiment is not limited tothe model specific printer driver. For example, the printer driver maybe a common printer driver provided by a printer vender which iscompatible to printing apparatuses of a plurality of types of theprinter vender. In addition, the printer driver may be a class driver(standard printer driver using a standardized printing method) that canbe commonly used by printing apparatuses provided by a plurality ofvenders corresponding to a driver provided as one of functions in apackage of the OS together with the OS.

When a user instructs printing from a Universal Windows Platform (UWP)application 202, a predetermined screen is displayed by Modern PrintDialog (MPD) corresponding to a function of the OS which is notillustrated in the drawing. The UWP application 202 is a drawingapplication for generating drawing data (such as an image or textinformation which becomes a source for forming a print on paper). Ascreen provided by the MPD includes a print preview function with whicha print result can be checked on the screen and a function with whichthe user can select a basic print setting.

FIGS. 3A to 3C illustrate examples of a specific screen displayed at thetime of the print setting. In FIG. 3A, when a print instruction isissued on a screen 301 provided by the UWP application serving as thedrawing application, a setting screen 302 illustrated in FIG. 3B isdisplayed by the MPD of the OS. The user can select a driver to be usedon the setting screen 302. Furthermore, a basic print setting can alsobe instructed on the setting screen 302.

Furthermore, the MPD activates Windows Store Device Application(hereinafter, WSDA) 207 where a detailed print setting can be selectedby the user in response to the instruction from the user. Specifically,when an “other setting” button 303 is specified on the setting screen302 of FIG. 3B, a detail setting screen 304 provided by the WSDA whichis illustrated in FIG. 3C is displayed. The user can specify a furtherdetailed print setting on the detail setting screen 304. The WSDA 207 isan application for extending a function of a printer driver 201 which isprovided by a vender that provides the printing apparatus (hereinafter,a printer vender). It should be noted that an image looking like anoriginal (document) image displayed on a right side within the detailsetting screen 304 provided by the WSDA of FIG. 3C is a sample imageoriginally included in the WSDA. That is, this sample image is not apreview image based on the drawing data generated by the UWP applicationbut is the sample image that does not change even when the drawing datais changed.

The WSDA 207 receives information indicating the print setting from theMPD and changes the setting information in accordance with the settingby the user to be returned to the MPD. Herein, the informationindicating the print setting is described in an XML format on the basisof a form defined by the OS and is included data called Print Ticket.The WSDA 207 can refer to and change the Print Ticket but does not referto the drawing data.

It should be noted that the Print Ticket is generated by a configurationmodule 208 of the selected printer driver 201. The WSDA 207 generates(edits) the Print Ticket on which the specification by the user isreflected by calling the configuration module 208.

The configuration module 208 also includes a function for generatingPrint Capabilities in which functions that can be set by the selectedprinter driver 201 and selection items are described in the XML formaton the basis of the form defined by the OS. The WSDA 207 or PEX 209which will be described below provides the user interface on the basisof information described in the Print Capabilities. An editingapplication 205 which will be described below can obtain the PrintCapabilities generated by the configuration module 208 via the functionof the OS.

It should be noted that the configuration module 208 is described as thefunction of the printer driver 201 in FIG. 2, but the configurationmodule 208 is originally a component of the OS. However, since thedriver itself is not provided with a configuration module in the V4printer driver, the configuration module 208 corresponding to thecomponent of the OS is used as the configuration module of the driver.The printer vender can customize an operation of the configurationmodule 208 by GPD or Javascript (registered trademark) Constraint, whichis not illustrated in the drawing, included in the printer driver 201.

When a “print” button is instructed on the setting screen 302 providedby the MPD of the OS after the print setting illustrated in FIGS. 3A to3C, a print request is issued. When the printing is instructed by theuser on the MPD, the request is received from the MPD, and the UWPapplication 202 generates printing data used for the printing. Thisprinting data corresponds to an XPS document described in a form calledXML Paper Specification (hereinafter, XPS) and is also referred to asintermediate data. The printing data according to the present exemplaryembodiment includes the above-described Print Ticket and the drawingdata generated by the drawing application.

The XPS document generated by the UWP application 202 is passed over toan editing app launcher 204 corresponding to a component of the OS. Theediting app launcher 204 determines whether or not the editingapplication 205 associated with the printer driver 201 via DeviceMetadata (hereinafter, which will be also simply referred to asMetadata) exists and is also configured to be activated. In a case whereit is determined that the editing application 205 exists and is alsoconfigured to be activated, the editing application 205 is activated. Itshould be noted that, in a case where the relevant editing application205 does not exist, the editing app launcher 204 stores the XPS documentas a spool file 206.

Herein, a relationship between the WSDA 207 and the editing application205 will be described. The WSDA 207 is an extension application forextending the function of the printer driver. Specifically, when adriver that does not include a function for providing a graphical userinterface (hereinafter, “GUI” or simply also referred to as “userinterface”) like the V4 printer driver is selected, the WSDA 207 canprovide the GUI such as the print setting screen. However, the WSDA 207does not provide a function for urging the user to perform any operationby displaying the GUI at a timing when the print request from the useris generated like the V3 printer driver. In view of the above, accordingto the present exemplary embodiment, the editing application 205 thatoperates in response to the print request from the user is used.

The editing application 205 is called Print Workflow Application and isan extension application for extending the function of the printerdriver 201 which is provided by the printer vender similarly as in theWSDA 207. That is, in a case where the driver that does not include thefunction for providing the GUI like the V4 printer driver is selected,it is possible to provide the GUI such as the print setting screen onthe basis of the instruction of the OS. It should be noted that, in acase where the V3 printer driver including the function for providingthe GUI is selected, the OS does not activate the editing app launcher204 but stores the XPS document generated by the drawing application asthe spool file 206. That is, in a case where the V3 printer driver isselected, the editing application 205 is not activated, and the GUI isnot provided.

It should be noted that both the WSDA 207 and the editing application205 are separate applications since the WSDA 207 and the editingapplication 205 are not provided as one of the components of the printerdriver 201. In addition, the WSDA 207 and the editing application 205can be configured together as one application, but for convenience, theWSDA 207 and the editing application 205 will be described herein as theseparate applications to describe a difference from the related-artWSDA.

The WSDA 207 and the editing application 205 are obtained in general bythe OS from an application distribution system which is not illustratedin the drawing (corresponding to a server managed by Microsoft(registered trademark)) via the Internet. The printer vender previouslyprovides the Metadata to a server for the Metadata which is managed byMicrosoft (registered trademark). Therefore, the appropriate WSDA 207and the appropriate editing application 205 are automatically installedinto the host computer 101. In more detail, device identificationinformation (Hardware ID) of the printing apparatus functioning as thedevice and software identification information (Identity Name) of theWSDA and the editing application are described in the Metadata. Deviceidentification information (Hardware ID) is described in an Inf file ofthe printer driver. Therefore, when the printer driver is installed, theOS downloads the corresponding Metadata on the basis of the deviceidentification information. The OS then refers to the Metadata andidentifies software identification information (Identity Name)associated with the corresponding device identification information(Hardware ID), so that it is possible to obtain the corresponding WSDAand the corresponding editing application. Therefore, the printer driver201 is associated with the WSDA 207 and the editing application 205.

The editing application 205 can display the user interface where theoperation instruction is accepted from the user. The editing application205 can also receive the XPS document corresponding to the printing dataand edit the Print Ticket and the drawing data in the XPS document. Itshould be noted that the WSDA 207 corresponding to the same extensionapplication can display the user interface but does not obtain the XPSdocument and does not refer to or edit the drawing data in the XPSdocument.

When the editing application 205 outputs the XPS document edited asneeded, the OS stores the XPS document as the spool file 206. When thespool file 206 is stored, a file pipeline manager (not illustrated) inthe printer driver 201 starts processing, and the number of filters andthe order are controlled by a configuration file (not illustrated). Thefile pipeline manager is a system in which the printing is performedthrough a plurality of filters. A filter group 210 according to thepresent exemplary embodiment is configured by including a layout filter211 functioning as a layout processing unit and a print command filter212 functioning as a print command conversion unit. It should be notedthat the file pipeline manager operates as the function of the printerdriver 201, but the file pipeline manager itself is originally thecomponent of the OS. However, since the driver itself is not providedwith the file pipeline manager in the V4 printer driver, the filepipeline manager corresponding to the component of the OS is used as thefunction of the driver.

The layout filter 211 includes a function for performing layoutprocessing of pages on the basis of the print setting information whilethe XPS document stored in the spool file 206 is set as an input andoutputting the laid-out XPS document. The layout processing includes,for example, layout printing for printing a plurality of pages on asingle sheet surface or poster printing for printing a single page on aplurality of sheet surfaces.

The print command filter 212 has a function for converting the XPSdocument corresponding to the intermediate data into a print commandthat can be interpreted by the printing apparatus 102 to be output inaccordance with the print setting information while an output from thelayout filter 211 is set as an input. The print command filter 212 isreferred to as a render filter in general in a case where the printcommand filter 212 temporarily converts the XPS document as the inputinto image data. The render filter is used in a printer driver for aninexpensive raster printer represented by an inkjet printer in manycases. In a case where the print command filter 212 operates as therender filter, the XPS document as the input is temporarily convertedinto image data. Thereafter, after the course of image processing suchas color space conversion or binarization, the image data is convertedinto a print command that can be interpreted by the raster printer.

In a case where types of print commands which can be interpreted by theprinting apparatus 102 include the XPS in a high-function printerrepresented by a page printer, the print command filter 212 edits theXPS document as the input and outputs the XPS document. When the XPSdocument does not need to be processed in the print command filter 212,the XPS document as the input may be output as it is, or a configurationmay also be adopted in which the print command filter 212 is notincluded in the printer driver 201. The above-described processing isthe basic processing for the printing from the UWP application 202.

It should be noted that, in a case where the drawing application is aLegacy application 203 such as a Win32 application, to set the printsetting, Printer Extensions 209 (hereinafter, PEX) are activated insteadof the WSDA. The PEX 209 is activated via the configuration module 208and can provide the user interface where the user can specify the printsetting. The PEX 209 may be provided together with the printer driver201 as a component in a driver package or may also be separatelydistributed. Similarly as in the WSDA 207, the PEX 209 can refer to andchange the Print Ticket but does not obtain the XPS document. Inaddition, the PEX 209 does not refer to and change the drawing data inthe XPS document. The PEX 209 is activated only in a case where the userissues an instruction on the Legacy application 203 and is notnecessarily activated at the time of the printing. When the printing isinstructed on the Legacy application 203, the Legacy application 203generates the XPS document as the printing data. Then, the XPS documentoutput from the Legacy application 203 is obtained and output by theediting application 205. Since the subsequent flow is equivalent to thecase of the printing processing from the UWP application 202, thedescriptions thereof will be omitted.

Configuration of XPS Document

Herein, the XPS document will be briefly described with reference toFIG. 12. The XPS document has a tree structure in whichFixedDocumentSequence (hereinafter, FDS) is set as a root. The FDSincludes a plurality of FixedDocuments (hereinafter, FD), and the FDincludes a plurality of FixedPages (hereinafter, FP). The FP describescontents of the page of the document in the XML format and includescontents to be actually displayed or printed. Each of the FDS, the FD,and the FP may be referred to as an XPS part in some cases. A resourcesuch as a font or an image used in the page contents of the FP can beshared by a plurality of FPs. Each of the FDS, the FD, and the FP canalso hold the print setting by the Print Ticket. Herein, the printsetting used when each of the FPs is to be printed corresponds to thePrint Ticket in which the Print Ticket of the FDS, the Print Ticket ofthe parent FD of the printing target FP, and the Print Ticket of theprinting target FP are merged into one another. It should be noted thatthe Print Ticket of the FDS is also referred to as the Print Ticket ofthe job.

FIG. 12 is an example of a block diagram illustrating a logicalstructure of the XPS document. The logical structure of the XPS document401 is a tree structure in which the FDS 402 is set as a root. The FDS402 includes the FD 403 and the FD 404 as children. The FD 403 includesthe FP 405 and the FP 406 as children. The FD 404 includes the FP 407 asa child. With regard to the Print Ticket in which the print setting isdescribed, the FDS 402 holds a Print Ticket 408. The FD 403 holds aPrint Ticket 409. The FP 405 holds a Print Ticket 410. The FD 404 holdsa Print Ticket 412. Herein, the Print Ticket 408 of the FDS 402corresponds to the Print Ticket of the job. Both the Print Ticket 409 ofthe FD 403 and the Print Ticket 412 of the FD 404 correspond to thePrint Ticket of the document. The Print Ticket 410 of the FP 405 in thelower layer corresponds to the Print Ticket of the page.

In FIG. 12, the FP 406 and the FP 407 do not hold the Print Ticket.Herein, for example, the Print Ticket used when the FP 405 is printedcorresponds to the Print Ticket in which the Print Ticket 408, the PrintTicket 409, and the Print Ticket 410 are merged into one another. Boththe FP 406 and the FP 407 that do not hold the Print Ticket use thePrint Ticket in a higher-level layer. For example, the Print Ticket usedwhen the FP 406 is printed corresponds to the Print Ticket in which thePrint Ticket 408 and the Print Ticket 409 are merged into each other.

It should be noted that, in FIG. 12, the FP 405 and the FP 406 share aresource 411 such as a font or an image, and the FP 507 uses a resource413 such as a font or an image. Furthermore, the FP 407 holds athumbnail image 414.

Setup Processing for Editing Application

FIG. 4 illustrates a main processing flow in the setup processing of theediting application 205 in the present printing system. Hereinafter, theediting application 205 may be described as the subject for therespective processes in some cases, but in actuality, the correspondingfunction is realized when the CPU 111 executes the corresponding program(program of the editing application 205. It should be noted that all theprocesses are not necessarily sequentially executed on the singleprocess, and a case may also occur where the process temporarily shiftsto the OS side, and then the process is called again from the OS. Thisis merely a flow illustrating the main processing of the editingapplication 205 in an understandable way for convenience.

When the XPS document is received from the drawing application at theprint request source, the editing app launcher 204 calls theinitialization processing of the editing application 205 associated withthe printing apparatus 102. It should be noted that the print request isissued when the “print” button is instructed on the setting screen 302provided by the OS after the above-described print setting describedwith reference to FIGS. 3A to 3C is performed, and the XPS document isoutput from the drawing application. The editing application 205registers the setup processing illustrated in FIG. 6 and editing and endprocessing illustrated in FIG. 8 which will be described below as theevent handler specified by the OS in the initialization processing. Whenthe editing application 205 ends the initialization processing, the OSexecutes the setup processing of the editing application 205 registeredas the specified event handler. FIG. 4 illustrates the setup processing.

First, the editing application 205 obtains the Print Ticket of the jobwhich is stored in the XPS document (S401). As described with referenceto FIG. 2, the Print Ticket is data including the information indicatingthe print setting and is generated by the configuration module 208 onthe basis of the print setting instructed by the user. The Print Ticketcan be obtained from the XPS document by calling a predetermined API ofthe OS.

Next, a reference is made to the obtained Print Ticket of the job, andit is checked whether or not a print preview activation instructionexists (S402). A specific checking method for the Print Ticket will bedescribed with reference to FIG. 6. The print preview activationinstruction may also be realized by a method other than the Print Ticketas long as a specification can be performed from the WSDA 207 or the PEX209 and also a reference can be made from the editing application 205.For example, a configuration may be adopted in which UserPropertyBag orQueuePropertyBag provided by the OS is used as a storage location of thesetting information of the printer driver 201. It should be noted thatthe print preview refers to displaying of the image of the print resultwhich is to be generated on the sheet surface on the basis of the printsetting and the drawing data generated by the drawing application on thedisplay unit 119. That is, a state in which “the print previewactivation instruction exists in the Print Ticket” indicates thatdisplaying on a print preview screen is instructed by the user. When theuser observes the print preview screen, before the printing, the userchecks whether or not a desired print result is to be obtained, andcorrection of the print setting, deletion of a particular page, orcancellation of the printing processing can be instructed whennecessary.

In S402, in a case where it is determined that the print previewactivation instruction exists, the editing application 205 saves storageinformation indicating that the print preview is “enabled” (S403). ALocal Storage provided by the OS is used for the holding of theinformation of the editing application 205 described in the processingin S403 and subsequent steps, for example. The storage informationstored in the Local Storage is information associated with the printsetting, and a detail thereof will be described below with reference toFIG. 10.

Thereafter, the specified API provided by the OS is called, and theprovision of the user interface is instructed in the subsequentprocessing of the editing application 205 (S404). When this API isexecuted, the UI processing of the editing application 205 illustratedin FIG. 7 which will be described below is called, and the editingapplication 205 displays the user interface.

In S402, in a case where it is determined that the print previewactivation instruction does not exist, the editing application 205 savesa state indicating the print preview is “disabled” in the storageinformation in the Local Storage (S405).

As described above, in the setup processing of the editing application205, the editing application 205 determines whether or not theactivation of the user interface is needed. In a case where theactivation of the user interface is needed, the activation isinstructed, and also information used for the subsequent processing isstored.

Configuration Examples of Print Ticket and Print Capabilities

FIG. 5 illustrates an example of the Print Capabilities of the printerdriver. It should be noted that, with regard to these PrintCapabilities, parts necessary for the descriptions are mainly described,and some parts are omitted.

In the Print Capabilities, a function that the driver includes (Feature)and setting items that can be set in the respective functions (Option)are represented. In the example of FIG. 5, Print Capabilities 500represent that plain paper (Plain) and photo paper (PhotoPaper) can beset as a media type (PageMediaType).

FIG. 6 illustrates an example of the Print Ticket generated on the basisof the Print Capabilities 500 of the printer driver illustrated in FIG.5. As illustrated in FIG. 6, setting values of the respective functionsdefined by the Print Capabilities are stored in the Print Ticket. Forexample, the Feature corresponding to psk:PageMediaType indicates amedia type used for the printing. The Print Ticket in FIG. 6 indicatespsk:Plain. That is, plain paper is specified. The determinationprocessing on the presence or absence of the print preview activationinstruction in S402 determines whether or not a specified value of theFeature corresponding to ns0000:JobPreview is ns0000:ON.

UI Processing of Editing Application

In a case where the display specification of the UI in S404 is executed,the OS calls the UI processing of the editing application 205 after thesetup processing of the editing application 205 is ended. FIG. 7illustrates a main processing flow in the UI processing of the editingapplication 205 in the present printing system. Hereinafter, the editingapplication 205 may be described as the subject for the respectiveprocesses in some cases, but in actuality, the corresponding function isrealized when the CPU 111 executes the corresponding program. It shouldbe noted that all the processes are not necessarily sequentiallyexecuted on the single process, and a case may also occur where theprocess temporarily shifts to the OS side, and then the process iscalled again from the OS. This is merely a flow illustrating the mainprocessing of the editing application 205 in an understandable way forconvenience. It should be noted that, in a case where the displayspecification of the UI in S404 is not executed, the OS skips the UIprocessing illustrated in FIG. 7 and calls the editing and endprocessing which will be described below.

First, the editing application 205 obtains the Print Ticket of the jobby using the predetermined API of the OS (S701). The editing application205 is provided with a device that obtains the Print Ticket of the jobas the function of the OS. When this is used, the editing application205 can easily refer to and change the print setting of the job withoutdirectly dealing with the Print Ticket in the XPS document. In addition,the Print Ticket of the job can be obtained before the XPS document iscompletely generated, which contributes to improvement in performancesince the processing is performed in advance. Furthermore, the editingapplication 205 obtains the Print Capabilities by using thepredetermined API of the OS on the basis of the obtained Print Ticket(S702).

Next, the editing application 205 configures (generates) a userinterface including a control item with which it is possible to specifythe function to be provided in the print preview on the basis of theobtained Print Ticket and PrintCapability (S703).

The editing application 205 then obtains the XPS document by using thepredetermined API of the OS (S704). Furthermore, the editing application205 analyzes the contents of the XPS document and displays the screenbased on the XPS document on the display unit 119 (S705).

As an example of the user interface generated by the editing application205, FIG. 8 illustrates an example of the print preview screen providedby the editing application 205. A display item 801 is a control item forchanging a page to be displayed on the print preview. The user canchange the displayed page by using this control item and also check thecurrent printing data and a total number of pages for the printinggenerated in the print setting. A display item 802 is a print previewscreen displaying an image of the print result on a specified page. Adisplay item 803 is a control item for specifying a layout printingfunction. A display item 804 is a control item for specifying a mediatype. Since the functions that the driver includes (functions supportedby the driver) are displayed by the display items 803 and 804, asdescribed above, the selection items are pursuant to the PrintCapabilities. Display items 805 and 806 are control items for specifyinga print range. The user can specify a type of the print range by thedisplay item 805. Types of the print range include “print all pages”,“print specified range”, and the like. The user can also specify theprint range when “print specified range” is selected in the display item805 by the display item 806. In the example of FIG. 8, the first pageand the second page are specified as the printing target. It should benoted that the printer driver 201 in the present example is not providedwith a function for changing the print range. That is, the changefunction for the print range is not described in the PrintCapability ofthe printer driver 201 in the present example. A display item 807 is abutton for starting the printing. A display item 808 is a cancel button.When the user presses this cancel button, the subsequent printingprocessing is cancelled.

According to the present exemplary embodiment, the editing application205 can realize the more accurate print preview by reflecting thesetting values set in the Print Ticket.

The XPS document obtained by the editing application 205 is generated bythe drawing application at the print request source and is data beforethe printer driver 201 processes. In other words, the editingapplication 205 obtains the XPS document before the printer driver 201does. Therefore, for example, even when the setting of the layoutprinting is specified in the Print Ticket in the XPS document, thelayout processing is not applied to the drawing data in the XPS documentwhich is received by the editing application 205. While theabove-described case is considered, the editing application 205 candisplay the print preview screen on which the print settings arereflected on the display unit 119. In a case where the print setting ischanged on the user interface displayed by the editing application 205,the editing application 205 displays the print preview screen on whichthe above-described change is reflected on the display unit 119 again.

It should be noted that two methods exist as the data creating methodfor the preview display of the editing application 205. The first methodis a method for the editing application 205 to edit the drawing data ofthe XPS document itself. In the case of this method, the editingapplication 205 performs the editing for reflecting the setting of thelayout printing with respect to the drawing data. The second method is amethod of changing a method for the display of the drawing data whilethe editing application 205 does not edit the drawing data of the XPSdocument. In the case of this method, when a 2-in-1 layout setting isadopted, for example, it looks on appearance as if the setting of thelayout printing is reflected when the editing application 205 merelyarranges two pages in the drawing data together. In S705, it is assumedthat the preview display is performed by using the second method.However, the preview display according to the present exemplaryembodiment can also be executed by using the first method.

When the editing application 205 accepts an input from the user (S706)and the printing is instructed on the user interface illustrated in FIG.8, the setting values of the respective functions which are specified bythe user are saved in the Local Storage as the storage information ofFIG. 10 (S707). With the above-described processes, the UI processing ofthe editing application 205 is ended.

According to the present configuration, it is possible to realize theprint preview function for displaying the print image close to the printresult on the basis of the drawing data generated by the drawingapplication and the print setting specified by the user before theprinting is performed. In addition, it is possible to perform a changefor a final adjustment of the print setting while the print result andthe number of print pages are checked on the print preview screenprovided by the editing application 205. With these functions, it ispossible to provide a final adjustment device that fits the printingwithin a desired number of pages, for example, while misprinting isavoided.

Interface Used by Editing Application 205

In this manner, when the editing application 205 is used, it is possibleto provide the function that is not provided by the WSDA 207 alone.However, the following deliberation is needed since the editingapplication 205 is activated in response to the print request from theuser. That is, when the editing application 205 is activated in responseto the print request, the editing application 205 regularly obtains andoutputs the XPS document. In other words, the editing application 205 isactivated when a situation is matched with an activation condition evenin a case where the function is not to be provided to the user. Forexample, in a case where the print preview function is provided by theediting application 205, the editing application 205 is activated evenwhen the user does not use the print preview function, and the editingapplication 205 obtains and outputs the XPS document. As a result, evenwhen the user does not use the preview function, there is a possibilitythat performance may be decreased simply because the editing applicationexists.

In the editing application 205, as an input and output interface wherethe obtainment and the output of the XPS document are performed, twotypes of access methods including an interface in a stream format and aninterface in a document format exist. The XPS document is treated as abyte stream as it is in the interface in the stream format. That is, thedata obtained in the stream format is obtained by collecting the XPSparts together to be subjected to ZIP compression. Therefore, thedecrease in performance is suppressed in the case of the interface inthe stream format. It should be noted that the XPS parts mentionedherein refer to the FDS, the FD, the FP, the Print Ticket attached tothose, and the resource such as the image or the font. However, in acase where the data obtained by using the interface in the stream formatis to be edited, the data in the byte stream needs to be analyzed, andcomplex processing is needed. On the other hand, the XPS document istreated as a package having an API where accesses can be made to therespective XPS parts in the interface in the document format. In a casewhere the interface in the document format is used, the editingapplication 205 obtains the XPS document in a format called objectmodel. The XPS document is treated in units of XPS part and is input andoutput for each of the XPS parts in the interface in the documentformat. For this reason, in a case where the interface in the documentformat is used, it is not necessary to analyze the XPS document toextract the XPS parts. Therefore, the editing of the XPS document iseasier for the data obtained by using the interface in the documentformat than the stream format. However, since the data analysis isneeded for the package generation, the processing is not started untilpieces of necessary data in the XPS document are obtained, and thedecrease in performance may occur.

In view of the above, according to the present exemplary embodiment, anappropriate interface is used as the input and output interface of theXPS document in the editing application 205. Hereinafter, a detailthereof will be described. It should be noted that any one of the streamformat and the document format may be used since the input and outputinterface of the XPS document in the UI processing of the editingapplication 205 in FIG. 7 does not involve the editing of the XPSdocument. It should be noted that the interface in the document formatmay be used in a case where the editing of the XPS document is performedat the time of the display processing in S705.

The processing of the editing application 205 in FIG. 4 and FIG. 9 isprocessing in a background, and the processing of the editingapplication 205 in FIG. 7 is processing in a foreground.

Editing and End Processing of Editing Application

The editing processing of the editing application 205 will be describedwith reference to FIG. 9. After the UI processing of the editingapplication 205 in FIG. 7 is ended, the OS calls the editing and endprocessing of the editing application 205 of FIG. 9. It should be notedthat, in a case where the display specification of the UI processing inS404 is not executed, the OS calls the present processing withoutcalling the UI processing of the editing application 205 in FIG. 7.Hereinafter, the editing application 205 may be described as the subjectfor the respective processes in some cases, but in actuality, thecorresponding function is realized when the CPU 111 executes thecorresponding program. In addition, all the processes are notnecessarily sequentially executed on the single process, and a case mayalso occur where the process temporarily shifts to the OS side, and thenthe process is called again from the OS. This is merely a flowillustrating the main processing of the editing application 205 in anunderstandable way for convenience.

The editing application 205 reads the UI display information in thestorage information saved in S403 (S901). In 5902, the editingapplication 205 determines whether or not the UI display is performed.In S902, in a case where it is determined that the UI display is notperformed, the use of the interface in the stream format is decided, andthe editing application 205 obtains the XPS document by using theinterface in the stream format (S903). This is because the use of theinterface in the stream format is beneficial in terms of performancesince the UI display does not exist and accordingly the editing of theXPS document is not needed.

Furthermore, the editing application 205 outputs the XPS documentobtained in S903 as it is without editing by using the interface in thestream format similarly as in the case of the obtainment (S904). Whenthe editing application 205 outputs the XPS document, the OS stores theXPS document as the spool file 206. Then, the processing by the printerdriver 201 is started.

In S902, in a case where it is determined that the UI display isperformed, the editing application 205 reads information associated withthe print setting saved in S707 as the storage information (S905). InS906, the editing application 205 determines whether or not the userperforms the setting change before and after the UI display. In S906, ina case where it is determined that the setting change is not performedbefore and after the UI display, the editing application 205 obtains theXPS document by using the interface in the stream format (S903). Then,the XPS document is output as it is by using the interface in the streamformat (S904). This is because the use of the interface in the streamformat is beneficial in terms of performance since the changeinstruction of the setting is not performed and accordingly the editingof the XPS document is not needed.

In S906, in a case where it is determined that the setting change isperformed, the editing application 205 determines whether or not thesetting in which the editing of the Print Ticket of the job by theediting application 205 is needed exists in the changed setting (S907).In a case where the setting in which the editing of the Print Ticket isneeded exists in the changed setting, the editing application 205obtains the Print Ticket of the job by using the predetermined API ofthe OS (S908). The editing application 205 then performs the editing ofthe Print Ticket of the job to reflect the setting value related to thedriver function in the storage information obtained in S905 on the PrintTicket of the job (S909). It should be noted that the driver functionrefers to a function that the printer driver 201 includes (which issupported by the printer driver 201). A configuration of the informationstored in the Local Storage and a method for the reflection onto thePrint Ticket of the job to realize these processes will be describedbelow with reference to FIG. 10. It should be noted that, in a casewhere a plurality of driver functions that have been changed by the UIinput in S706 exist, the editing application 205 performs the processingfor reflecting the setting values of all the driver functions on thePrint Ticket of the job.

Next, in S910, the editing application 205 determines whether or not thesetting in which the editing of the XPS document by the editingapplication 205 is needed exists in the changed setting. In thisdetermination, it is determined whether or not the editing by theediting application 205 is needed with regard to at least one of thedrawing data in the XPS document and the Print Ticket in the XPSdocument (except for the Print Ticket of the job). It should be notedthat a reason why the Print Ticket of the job is excluded from thedetermination target in S910 is that the editing of the Print Ticket ofthe job has been performed already in S907 to S909.

In a case where it is determined that the setting in which the editingof the XPS by the editing application 205 is needed does not exist inthe setting changed in S910, the use of the interface in the streamformat is decided. The editing application 205 than obtains and outputsthe XPS document by using the interface in the stream format (S903,S904). In a case where it is determined that the setting in which theediting of the XPS by the editing application 205 is needed exists inthe setting changed in S910, the use of the interface in the documentformat is decided. The editing application 205 then obtains the XPSdocument by using the interface in the document format (S911).

In S912, the editing application 205 performs the editing of the XPSdocument obtained in S911 on the basis of the function specified by theuser and the setting value thereof. The editing application 205 thenoutputs the edited XPS document by using the interface in the documentformat (S913). When the editing application 205 outputs the edited XPSdocument, the OS stores the edited XPS document as the spool file 206.When the XPS document is stored in the spool file 206, the processing bythe printer driver 201 is started.

It should be noted that the editing application 205 determines whetheror not the editing of the Print Ticket of the job is needed and obtainsand edits the Print Ticket of the job in S907 to S909 before theobtainment of the XPS document in S911 in FIG. 9. That is, the editingapplication 205 refers to and changes the print setting of the jobwithout directly dealing with the Print Ticket in the XPS document. Thisis because, as also described in the processing in S701, the PrintTicket of the job can be obtained before the XPS document is completelygenerated. The obtainment of the Print Ticket of the job and the editingprocessing are performed in advance, which contributes the improvementin performance. However, the present exemplary embodiment is not limitedto this. S907 to 909 may be omitted. That is, it may be determined inS910 whether or not the editing of the XPS document is needed whileincluding the determination on whether or not the editing of the PrintTicket of the job is needed. In S912, the editing of the XPS documentmay be executed while including the editing of the Print Ticket of thejob.

Here, the storage information stored in the Local Storage will bedescribed with reference to FIG. 10. FIG. 10 illustrates an example ofthe information stored in the Local Storage. The storage information isconstituted by a name and a value and includes information associatedwith the print setting.

In the processing in S403 of FIG. 4, to indicate that the UI display isenabled, a setting value of ON information under the name of RequestUIis added to the Local Storage. In addition, in the processing in S405,to indicate that the UI display is disabled, a setting value of OFFinformation under the name of RequestUI is added to the Local Storage.

In the processing in S707 of FIG. 7, the setting values of therespective functions specified by the user on the print preview screenare saved in the Local Storage. In the example of FIG. 10, it is assumedthat the user changes three settings including Page Layout, Pages, andRange on the preview screen of FIG. 8.

An item having a name of JobNUpAllDocumentsContiguously that is asetting item of the Print Ticket is stored in the Local Storage withrespect to the Layout change. Then, PagePerSheet_2 that is an Optionname corresponding to a setting item of the Page Layout specified by theuser is added to the above-described item as the setting value. That is,by the Layout change on the UI of FIG. 8, the information indicating thechange to the print setting is newly added into the storage informationthat is information associated with the print setting of FIG. 10.

With respect to the setting of the Pages, information in which Rangesindicating a range specification are set as the setting values are addedunder the name of Pages to the Local Storage. Since the rangespecification is specified in the Pages, information indicating thespecific range such as the information of the setting value indicatingthe print range of “1-2” is added under the name of Range to the LocalStorage. That is, due to the changes to the setting of the Pages and thesetting of the Ranges on the UI of FIG. 8, the information indicatingthe changes to the print setting is newly added into the storageinformation that is the information associated with the print setting ofFIG. 10.

In this manner, the reference is made to the storage information of FIG.10 which is stored in FIG. 4 and FIG. 7, and the processing in FIG. 9 isperformed. Specifically, in the processing in 5902, the editingapplication 205 checks the setting value in the RequestUI of FIG. 10. Ina case where the setting value is ON, it is determined that the UIdisplay is performed.

In the processing in S906, the editing application 205 also checks thesetting items on the second and subsequent columns in FIG. 10 which arestored in the Local Storage. In the case of FIG. 10, since pieces of theinformation of JobNUpAllDocumentsContiguously, Pages, and Range areadded, it is determined that the changes to the setting have beenperformed.

In the processing in S907, the editing application 205 determineswhether or not the change to the Print Ticket of the job is needed fromthe information stored in the Local Storage. Specifically, when it isdetermined that the setting with regard to the function supported by thedriver like the layout printing has been changed, it is determined thatthe change to the Print Ticket of the job is needed. In the example ofFIG. 10, since the information of JobNUpAllDocumentsContiguously isadded, it is determined that the setting of the layout printing has beenchanged, and it is determined that the change to the Print Ticket of thejob is needed.

In S909, the editing application 205 edits the Print Ticket of the job.Specifically, the setting value in the storage information is set as theOption with respect to the Feature in the Print Ticket corresponding tothe name of the storage information of FIG. 10. That is, the Option ofthe Feature corresponding to JobNUpAllDocumentsContiguously in the PrintTicket of the job of FIG. 6 is changed to PagePerSheet_2. As a result,the setting change instructed by the user is reflected on the PrintTicket of the job. Then, the printer driver 201 can generate the printcommand to be transmitted to the printer in accordance with the settingof the Print Ticket. That is, in the case of the present example, inorder for the printer driver 201 to execute the layout printing forprinting two pages on one sheet on the basis of the Print Ticket of thejob, the printer driver 201 generates the print command by editing thedrawing data in the XPS document.

In the processing in S910, the editing application 205 determineswhether or not the change in which the editing of the XPS document bythe editing application 205 is needed exists on the basis of the storageinformation in the Local Storage. For example, in a case where theprinter driver 201 is not compatible to the function for the settingchange to the print range, the printer driver 201 does not change theXPS document for changing the print range. Therefore, the editing of theXPS document by the editing application 205 is needed, and in theabove-described case, it is determined that the change in which theediting of the XPS document is needed exists. In the example of FIG. 10,since the item of the Range is added, it is determined that the changesetting of the print range corresponding to the function that is notsupported by the printer driver 201 has been done, and it is determinedthat the editing of the XPS document by the editing application 205 isneeded.

In S912, the editing application 205 performs the editing of the XPSdocument. Specifically, since the print range is set as “from the firstpage to the second page” in the item of the Range of the storageinformation of FIG. 10, page data of the third and subsequent pages inthe drawing data of the obtained XPS document is deleted from the XPSdocument. As a result, the printer driver 201 generates the printcommand while the XPS document edited by the editing application 205 isset as the input. Therefore, the printer driver 201 itself can set onlythe specified range as the printing target without performing theediting of the XPS document for the change to the print range.

As described above, according to the present exemplary embodiment, whenthe editing application 205 is used, it is possible to provide the GUIin response to the print request. In addition, the editing of the PrintTicket of the job and the XPS document can be performed by the editingapplication 205 on the basis of the input of the print setting on theGUI provided by the editing application 205.

The printer drivers have different supported functions (functions thatcan be provided) depending on types. However, it is possible to reducefunction disparity based on the types of the printer drivers by theediting application 205 according to the present exemplary embodiment.That is, the editing application 205 can perform the editing of the XPSdocument with regard to the function that is not supported by theprinter driver (extension function). Therefore, even the function thatis not supported by the printer driver can be provided to the user. Inparticular, even the printer driver that has only a basic function suchas a standard printer driver can provide a function close to a modelspecific printer driver by using the editing application 205. It shouldbe noted that, with regard to the function supported by the printerdriver, after the editing for reflecting the setting change on the PrintTicket is performed, the printer driver may be in charge of editing thedrawing data of the XPS document. The editing application 205 maydetermine whether or not the function is a function supported by thedriver on the basis of the information related to the previously storedfunction and may also perform the determination by obtaining thePrintCapability.

The editing application 205 according to the present exemplaryembodiment uses the interface in the stream format in a case where theediting of the XPS document by the editing application 205 is notneeded. On the other hand, in a case where the editing of the XPSdocument by the editing application 205 is needed, the editingapplication 205 uses the interface in the document format. That is, in acase where the user does not use the print preview display or a casewhere the user does not perform the setting change even when the printpreview display is used, since the editing of the XPS document by theediting application 205 is not needed, the editing application 205 usesthe interface in the stream format. As a result, it is possible toreduce the influence of the decrease in performance which is caused bythe activation of the editing application 205. On the other hand, in acase where the editing of the XPS document by the editing application205 is needed, the editing of the XPS document by the editingapplication 205 can be performed by the use of the interface in thedocument format.

Second Exemplary Embodiment

Next, a second exemplary embodiment will be described. According to thefirst exemplary embodiment, the editing application 205 presents thefunction in which the setting can be changed to the user by displayingthe UI and determines whether or not the editing of the XPS document bythe editing application 205 is needed in accordance with the userinstruction. Then, the interface is switched depending on whether or notthe editing of the XPS document by the editing application 205 isneeded. On the other hand, according to the second exemplary embodiment,a feature resides in that the editing application 205 switches theinterface depending on whether or not the UI display by the editingapplication 205 is performed.

Since a hard configuration of the printing system is the same as that ofthe first exemplary embodiment, descriptions thereof will be omitted.With regard to the flows of the respective processes too, a flow is alsothe same as that of the second exemplary embodiment except for the flowof the editing and end processing of the editing application 205according to the first exemplary embodiment (FIG. 9). Therefore,different parts from the first exemplary embodiment will be mainlydescribed below.

FIG. 12 illustrates an example of the editing and end processingaccording to the second exemplary embodiment. After the UI processing ofthe editing application 205 in FIG. 7 is ended, the OS calls the editingand end processing of the editing application 205 in FIG. 12. It shouldbe noted that, in a case where the display specification of the UIprocessing is not executed in S404, the OS calls the present processingwithout calling the UI processing of the editing application 205 in FIG.7. Hereinafter, the editing application 205 may be described as thesubject for the respective processes in some cases, but in actuality,the corresponding function is realized when the CPU 111 executes thecorresponding program. In addition, all the processes are notnecessarily sequentially executed on the single process, and a case mayalso occur where the process temporarily shifts to the OS side, and thenthe process is called again from the OS. This is merely a flowillustrating the main processing of the editing application 205 in anunderstandable way for convenience.

The editing application 205 reads the UI display information in thestorage information of FIG. 10 which is saved in S403 (S1201). Then, inS1202, the editing application 205 determines whether or not the UIdisplay is performed. In S1202, in a case where it is determined thatthe UI display is not performed, the editing application 205 obtains theXPS document by using the interface in the stream format (S1203). Thisis because, when the UI display is not performed, the change to theprint setting is not performed, and accordingly the editing of the XPSdocument is not needed. Therefore, a benefit is attained in terms ofperformance by the use of the interface in the stream format.

In S1204, the editing application 205 outputs the XPS document obtainedin S1203 as it is without editing by using the interface in the streamformat. When the editing application 205 outputs the XPS document, theOS stores the XPS document as the spool file 206, and the processing bythe printer driver 201 is started.

In S1202, in a case where it is determined that the UI display isperformed, the editing application 205 reads the information associatedwith the print setting of FIG. 10 which is saved as the storageinformation in S707 (S1205). Next, the editing application 205determines whether or not the setting change in which the editing of thePrint Ticket of the job is needed exists in the storage information ofFIG. 10 (S1206). In a case where the setting change in which the editingof the Print Ticket of the job is needed exists, the editing application205 obtains the Print Ticket of the job by using the predetermined APIof the OS (S1207). The setting value related to the function supportedby the printer driver 201 (driver function) in the storage informationobtained in S1205 is then reflected on the Print Ticket of the job(S1208). It should be noted that, since the processing in S1201 to S1208is the same as the processing in S901 to S909 in FIG. 9 except for theexclusion of S906, the detail thereof is omitted.

Next, the editing application 205 obtains the XPS document by using theinterface in the document format (S1209). In S1210, it is determinedwhether or not the setting change in which the editing of the XPSdocument by the editing application 205 is needed exists on the basis ofthe storage information obtained in S1205. Although steps to proceedafter the determination are different in the determination processing inS1210, since the contents of the determination are the same as S910 inFIG. 9, the detail thereof will be omitted.

In S1210, in a case where it is determined that the setting change inwhich the editing of the XPS by the editing application 205 is neededexists in the storage information, the editing application 205 performsthe editing of the obtained XPS document on the basis of the functionspecified by the user and the setting value thereof (S1211). The editingapplication 205 than outputs the edited XPS document by using theinterface in the document format (S1212). It should be noted that theprocessing in S1211 and S1212 is the same as the processing in S911 andS912 in FIG. 9, and the detail thereof will be omitted.

In S1210, in a case where it is determined that the setting change inwhich the editing of the XPS by the editing application 205 is neededdoes not exist in the storage information, the editing application 205outputs the obtained XPS document without editing by using the interfacein the document format (S1212).

As described above, the editing application 205 according to the presentexemplary embodiment uses the interface in the stream format in a casewhere the UI display is not performed and uses the interface in thedocument format in a case where the UI display is performed. As aresult, in a case where the user does not use the UI function such asthe print preview function, the editing application 205 can suppress thedecrease in performance which is caused by the activation of the editingapplication 205.

Third Exemplary Embodiment

Next, a third exemplary embodiment will be described. According to thefirst exemplary embodiment and the second exemplary embodiment, theediting application 205 provides the function that can be set to theuser by displaying the UI. However, the editing application 205 canperform the editing of the XPS document without displaying the UI.Therefore, the editing application 205 according to the presentexemplary embodiment does not perform the instruction of the UI displayin the setup processing. When the instruction of the UI display is notperformed, the UI processing is not called, and the editing application205 executes the editing and end processing. For example, in a casewhere a particular watermark (stamp) is forcedly added in accordancewith a previously determined setting, the editing application 205 doesnot need the user instruction. Therefore, the editing application 205does not perform the UI display but performs the editing of the XPSdocument to add the watermark. Hereinafter, the processing according tothe present exemplary embodiment will be described in detail.

Since the hard configuration of the printing system is the same as thatof the first exemplary embodiment, descriptions thereof will be omitted.With regard to the flows of the respective processes too, partsdifferent from the first exemplary embodiment will be mainly described.

FIG. 11 illustrates an example of the editing and end processingaccording to the third exemplary embodiment. The OS calls the editingand end processing of the editing application 205 of FIG. 11 after thesetup processing of the editing application 205 of FIG. 4 is ended.Hereinafter, the editing application 205 may be described as the subjectfor the respective processes in some cases, but in actuality, thecorresponding function is realized when the CPU 111 executes thecorresponding program. In addition, all the processes are notnecessarily sequentially executed on the single process, and a case mayalso occur where the process temporarily shifts to the OS side, and thenthe process is called again from the OS. This is merely a flowillustrating the main processing of the editing application 205 in anunderstandable way for convenience.

The editing application 205 obtains previously stored setting compulsioninformation (S1101). It is conceivable to use UserPropertyBag orQueuePropertyBag provided by the OS as a storage location of theinformation, but the Print Ticket or the Local Storage may also be used.The setting compulsion information is previously set by a systemadministrator or the user itself. With regard to the setting compulsion,the particular watermark is added, or a duplex print setting is forcedlyturned ON, for example.

In S1102, the editing application 205 determines whether or not thesetting compulsion information exists. That is, the editing application205 determines whether or not a forcedly set function is registered evenwhen the setting from the user on the UI provided by the editingapplication 205 is not accepted.

In S1102, in a case where it is determined that the setting compulsioninformation does not exist, since the editing of the XPS document is notneeded, the editing application 205 obtains and outputs the data byusing the interface in the stream format (S1103, S1104). On the otherhand, in S1102, in a case where it is determined that the settingcompulsion information exists, since the editing of the XPS document isneeded, the editing application 205 obtains the data by using theinterface in the document format (S1105).

In S1106, the editing application 205 edits the obtained XPS document.In S1107, the editing application 205 outputs the edited XPS document byusing the interface in the document format.

It should be noted that, in a case where the forcedly set function isincluded in the driver function, it is sufficient when the editingapplication 205 reflects the setting on the Print Ticket in the XPSdocument. That is, it is sufficient when the editing application 205executes only the editing of the Print Ticket in the XPS documentwithout performing the editing of the drawing data in the XPS document.In the present example too, as in S910 in FIG. 9, a configuration mayalso be adopted in which the determination is previously made on whetheror not the setting change in which the change of the XPS document isneeded occurs, and the interface in the document format is used only ina case where the change to the XPS document is needed.

According to the present exemplary embodiment, also in a case where theediting of the XPS document is needed while the UI is not displayed, theediting application 205 can suppress the decrease in performance whichis caused by the activation of the editing application 205.

Other Embodiments

Embodiment(s) of the present invention can also be realized by acomputer of a system or apparatus that reads out and executes computerexecutable instructions (e.g., one or more programs) recorded on astorage medium (which may also be referred to more fully as a‘non-transitory computer-readable storage medium’) to perform thefunctions of one or more of the above-described embodiment(s) and/orthat includes one or more circuits (e.g., application specificintegrated circuit (ASIC)) for performing the functions of one or moreof the above-described embodiment(s), and by a method performed by thecomputer of the system or apparatus by, for example, reading out andexecuting the computer executable instructions from the storage mediumto perform the functions of one or more of the above-describedembodiment(s) and/or controlling the one or more circuits to perform thefunctions of one or more of the above-described embodiment(s). Thecomputer may comprise one or more processors (e.g., central processingunit (CPU), micro processing unit (MPU)) and may include a network ofseparate computers or separate processors to read out and execute thecomputer executable instructions. The computer executable instructionsmay be provided to the computer, for example, from a network or thestorage medium. The storage medium may include, for example, one or moreof a hard disk, a random-access memory (RAM), a read only memory (ROM),a storage of distributed computing systems, an optical disk (such as acompact disc (CD), digital versatile disc (DVD), or Blu-ray Disc(BD)TM), a flash memory device, a memory card, and the like.

While the present invention has been described with reference toexemplary embodiments, it is to be understood that the invention is notlimited to the disclosed exemplary embodiments. The scope of thefollowing claims is to be accorded the broadest interpretation so as toencompass all such modifications and equivalent structures andfunctions.

1. A control method implemented in an information processing apparatusby at least one processor that executes a function extending applicationthat is able to extend a function of a print software that generates aprint command and is able to perform editing of intermediate dataincluding drawing data generated by a drawing application, the controlmethod comprising: performing first obtaining processing to obtaininformation associated with a print setting; performing determinationprocessing to determine, on a basis of the obtained informationassociated with the print setting, which interface is selected forobtaining intermediate data including the drawing data, from a pluralityof interfaces; and performing second obtaining processing to obtain theintermediate data by using the selected interface, wherein the functionextending application is activated based on a print instruction, andperforms the first obtaining processing, the determination processing,and the second obtaining processing, and wherein the intermediate dataoutput from the function extending application after the first obtainingprocessing, the determination processing and the second obtainingprocessing, is obtained by the print software and converted into theprint command by the print software.
 2. The control method according toclaim 1, wherein the interface used for obtaining the intermediate datais selected based on determining whether or not the informationassociated with the print setting includes information associated with asetting that the editing of the intermediate data by the functionextending application is needed.
 3. The control method according toclaim 1, wherein an interface in a first format is determined as theselected interface among the plurality of interfaces in a case where theinformation associated with the print setting includes informationassociated with a setting that the editing of the intermediate data bythe function extending application is needed, and wherein an interfacein a second format different from the first format is determined as theselected interface among the plurality of interfaces in a case where theinformation associated with the print setting does not include thesetting that the editing of the intermediate data by the functionextending application is needed.
 4. The control method according toclaim 3, wherein the function extending application can provide agraphical user interface (GUI), and wherein the interface in the secondformat is determined as the selected interface in a case where the GUIis not provided by the function extending application.
 5. The controlmethod according to claim 4, wherein the interface in the second formatis determined as the selected interface in a case where a changeinstruction of the print setting by a user is not performed on the GUIprovided by the function extending application.
 6. The control methodaccording to claim 1, wherein the information associated with the printsetting is saved in accordance with the print setting in accordance witha user instruction on a GUI provided by the function extendingapplication, and wherein it is determined whether or not the editing ofthe intermediate data by the function extending application is needed ona basis of the information associated with the print setting saved inaccordance with the user instruction on the GUI.
 7. The control methodaccording to claim 1, wherein the function extending application canprovide a graphical user interface (GUI), wherein an interface in afirst format is determined as the selected interface among the pluralityof interfaces in a case where the information associated with the printsetting includes a setting that provision of the GUI by the functionextending application is needed, and wherein an interface in a secondformat different from the first format is determined as the selectedinterface among the plurality of interfaces in a case where theinformation associated with the print setting does not include thesetting that the provision of the GUI by the function extendingapplication is needed.
 8. The control method according to claim 4,wherein a screen including a print preview based on the drawing data anda display item for performing a change instruction of the print settingby the user is provided as the GUI.
 9. The control method according toclaim 3, wherein, in a case where the selected interface is in the firstformat and the editing of the intermediate data is performed, the editedintermediate data is output by using the selected interface in the firstformat, and wherein, in a case where the selected interface is in thesecond format, the obtained intermediate data is output by using theselected interface in the second format without editing the intermediatedata.
 10. The control method according to claim 3, wherein the interfacein the first format is an interface where the intermediate data isobtained part by part, and the interface in the second format is aninterface where the intermediate data is obtained in a stream format.11. The control method according to claim 3, wherein the interface inthe first format is an interface in a document format, and the interfacein the second format is an interface in a stream format.
 12. The controlmethod according to claim 1, wherein the function extending applicationis an application that is activated in a case where a printer driverthat does not include a function for providing a graphical userinterface (GUI) is selected and can provide the GUI.
 13. An informationprocessing apparatus comprising: at least one processor; and at leastone memory storing a function extending application that is configuredto extend a function of a print software that generates a print command,and is configured to perform editing of intermediate data includingdrawing data generated by a drawing application, the function extendingapplication causing, when executed by the at least one processor, theinformation processing apparatus to function as a first obtaining unitconfigured to obtain information associated with a print setting, adetermining unit configured to determine, on a basis of the obtainedinformation associated with the print setting, which interface isselected for obtaining the intermediate data including the drawing data,from a plurality of interfaces; and a second obtaining unit configuredto obtain the intermediate data by using the selected interface, whereinthe function extending application is activated based on a printinstruction, and wherein the intermediate data output from the functionextending application, after the intermediate data is obtained by thesecond obtaining unit , is obtained by the print software and convertedinto the print command by the print software.
 14. The informationprocessing apparatus according to claim 13, wherein the interface usedfor obtaining the intermediate data is selected based on determiningwhether or not the information associated with the print settingincludes information associated with a setting for which the editing ofthe intermediate data by the function extending application is needed.15. The information processing apparatus according to claim 13, whereinan interface in a first format is determined as the selected interfaceamong the plurality of interfaces in a case where the informationassociated with the print setting includes information associated with asetting for which the editing of the intermediate data by the functionextending application is needed, and wherein an interface in a secondformat different from the first format is determined as the selectedinterface among the plurality of interfaces in a case where theinformation associated with the print setting does not include thesetting for which the editing of the intermediate data by the functionextending application is needed.
 16. The information processingapparatus according to claim 15, wherein the function extendingapplication can provide a graphical user interface (GUI), and whereinthe interface in the second format is determined as the selectedinterface in a case where the GUI is not provided by the functionextending application.
 17. The information processing apparatusaccording to claim 16, wherein the interface in the second format isdetermined as the selected interface in a case where a changeinstruction of the print setting by a user is not performed on the GUIprovided by the function extending application.
 18. The informationprocessing apparatus according to claim 13, wherein the informationassociated with the print setting is saved in accordance with the printsetting in accordance with a user instruction on a GUI provided by thefunction extending application, and wherein it is determined whether ornot the editing of the intermediate data by the function extendingapplication is needed on a basis of the information associated with theprint setting saved in accordance with the user instruction on the GUI.19. The information processing apparatus according to claim 13, whereinthe function extending application can provide a graphical userinterface (GUI), wherein an interface in a first format is determined asthe selected interface among the plurality of interfaces in a case wherethe information associated with the print setting includes a setting forwhich provision of the GUI by the function extending application isneeded, and wherein an interface in a second format different from thefirst format is determined as the selected interface among the pluralityof interfaces in a case where the information associated with the printsetting does not include the setting for which the provision of the GUIby the function extending application is needed.
 20. The informationprocessing apparatus according to claim 16, wherein a screen including aprint preview based on the drawing data and a display item forperforming a change instruction of the print setting by the user isprovided as the GUI.
 21. The information processing apparatus accordingto claim 15, wherein, in a case where the selected interface is in thefirst format and the editing of the intermediate data is performed, theedited intermediate data is output by using the selected interface inthe first format, and wherein, in a case where the selected interface isin the second format, the obtained intermediate data is output by usingthe selected interface in the second format without editing theintermediate data.
 22. The information processing apparatus according toclaim 15, wherein the interface in the first format is an interfacewhere the intermediate data is obtained part by part, and the interfacein the second format is an interface where the intermediate data isobtained in a stream format.
 23. The information processing apparatusaccording to claim 15, wherein the interface in the first format is aninterface in a document format, and the interface in the second formatis an interface in a stream format.
 24. The information processingapparatus according to claim 13, wherein the function extendingapplication is an application that is activated in a case where aprinter driver that does not include a function for providing agraphical user interface (GUI) is selected and can provide the GUI.